will travis have enough resource to crossbuild ?

Please see the linked Travis log file. Needs an extra travis_wait but seems to build it.

Thanks,

The PoC is certainly interesting but it does need to follow the same flow as the other release procedures.
That means it needs to run the tests before even publishing a binary.

Sure, but I stopped here before spending time on something that might not be merged because there’s something fundamentally off with it.

Any other input as to how to proceed? Make tests run, spread to the supported node versions - anything else I should be aware of?

I'm going to have to consult the Travis docs a bit further, adding the ARM architecture will require additional builds for the different NodeJS versions. Electron also has an ARM version, so if we also want to provide those binaries we are looking at doubling the load of the CI essentially.

It does not seem to me that there is a max limit on the amont of jobs, rather just a max limit for each job.

To make it more production friendly:

• Restore the .travis.yaml file
• Move ARM specific setup code (Install & configure docker) into a new shell script unders the /scripts
• Have the original file build_against_node.sh run within that docker/qemu container (may need modification for the naming of the releases etc)

Note: You will need to pass the environment variables to the docker command in order to bridge the gap.

I have not abandoned this, just low on the todo list for the time being, so if anybody else feels like giving it a shot go right ahead.

See #1362